New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MUST BE CAREFULLY REVIEWED] saltcloud / lxc improvments #10869
Conversation
Test FAILed. |
Test FAILed. |
Test FAILed. |
@s0undt3ch, would you please take a close look at this? |
Note that lxc userspace tools v1.0 was released last week. It is a complete overhaul of the tools, and I think packages are going to be aggressively pushed out for current OS releases. While it is mostly backwards compatible, it did break the salt lxc module. I mention it here, as some of the updates for 1.0 (particularly the lxc.info function) would not be incompatible with this pull request. I should have my updates pushed out by end of day on Monday. |
what im doing is 1.0 only anyway. :) |
And, im thinking im now at 75%/80% done. |
(i think i wont have time to add much tests for the moment) |
rebased my current working copy, there must be debug and pdb in there ^^ |
Strangely github doesnt show commits in the order of my git log does |
Test FAILed. |
Test FAILed. |
Test FAILed. |
Test FAILed. |
Test FAILed. |
#10884 fixes one of the broken tests |
Test FAILed. |
Test FAILed. |
Test FAILed. |
Test FAILed. |
Test FAILed. |
I think that 100% of the stuff is there, im now doing some tests, but review can be done. Ping @thatch45 @s0undt3ch |
Test FAILed. |
Ok. My first observation is, can you submit the LXC stuff on another PR(even if one depends on the other, just mention it)? Does it really neend to be the same? My other comments will come a little later since inline commenting from the phone is not that great. |
Well, it will be tedious for me to locally have them separated as they are very dependant... Or if i inter-merge branches, then the history would be cluterred |
So i created #10897 & #10898 which on this PR is dependant, @s0undt3ch |
return ret | ||
|
||
|
||
def cloned(name, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought... would it make more sense to have a single present
state that delegates to created
and cloned
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the provision which does that is on salt-cloud, @mgwilliams.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it was does in state at a moment, but was removed and rebased for a long time :)
Test FAILed. |
import glob | ||
import time | ||
import signal | ||
import logging | ||
from pprint import pprint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you using this pprint
import?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uhm, not sure anymore
Test FAILed. |
provider as a special meaning in salt ... http://docs.saltstack.com/ref/states/providers.html
Test FAILed. |
[MUST BE CAREFULLY REVIEWED] saltcloud / lxc improvments
If you want to begin review, feel free but it is not finished.
Idea is to complete lxc modules , fix some salt cloud code (multiprocessing) and add a saltcloud lxc provider